Howdy and thanks for contributing to our repo. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.

Preview URL: https://03998e9e.preview.developers.cloudflare.com
Preview Branch URL: https://tori-19653-reactjs-framework-guide-for-workers.preview.developers.cloudflare.com

Files with changes (up to 15)

This looks good for people getting started. Approved pending the C3 template landing and the links being updated.

There is also a class of people who already have React/Vite projects who would like to deploy to Cloudflare. Do we have a format for migrating frameworks to Cloudflare?

@petebacondarwin I left you some inline questions. Once those are resolved, will this be ready to merge? (I ask because I see that your template is merged, but the original template this was created for isn't merged, and I'm not sure what the difference is.

To answer your question about migrating existing frameworks. That's a content gap we need to fill in. Is the process essentially the same for each framework guide? If so, we can create a "Migrate your existing project" partial and add it to each guide? If that sounds like the right approach, I think it would make sense to create that as a separate follow-up PR. Let me know. Thanks!
cc: @mikenomitch @nevikashah

@petebacondarwin I left you some inline questions. Once those are resolved, will this be ready to merge? (I ask because I see that your template is merged, but the original template this was created for isn't merged, and I'm not sure what the difference is.

Yes this docs update looks ready to merge once we resolve those two inline comments.

• The second one (a link to the Vite docs) is straightforward.
• For the first one, I think the quickest solution is not to mention Cloudflare bindings in this doc. This is in keeping with other non-full-stack frameworks, such as the Gatsby one: https://developers.cloudflare.com/workers/frameworks/framework-guides/gatsby/

@petebacondarwin I left you some inline questions. Once those are resolved, will this be ready to merge? (I ask because I see that your template is merged, but the original template this was created for isn't merged, and I'm not sure what the difference is.

Yes this docs update looks ready to merge once we resolve those two inline comments.

• The second one (a link to the Vite docs) is straightforward.
• For the first one, I think the quickest solution is not to mention Cloudflare bindings in this doc. This is in keeping with other non-full-stack frameworks, such as the Gatsby one: https://developers.cloudflare.com/workers/frameworks/framework-guides/gatsby/

@petebacondarwin Updated!

I have a PR up to graduate the Workers C3 template from experimental: cloudflare/workers-sdk#8371
When that lands this PR should be updated to remove the --experimental option and add --platform=workers option.

I have a PR up to graduate the Workers C3 template from experimental: cloudflare/workers-sdk#8371 When that lands this PR should be updated to remove the --experimental option and add --platform=workers option.

@petebacondarwin Just to clarify - I should hold off on merging this until that lands?

I have a PR up to graduate the Workers C3 template from experimental: cloudflare/workers-sdk#8371 When that lands this PR should be updated to remove the --experimental option and add --platform=workers option.

@petebacondarwin Just to clarify - I should hold off on merging this until that lands?

If it is ready to merge now, you can go ahead. I am going to merge the workers-sdk change now. But it will probably not be released until Tuesday now. So we can have a new PR for then.

Oh it seems we are going to release the workers-sdk changes today. So let's hold on merging this and fix it up to match the non-experimental C3 template.